-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
checkST2110: Add stricter a=mid position verification #12
base: master
Are you sure you want to change the base?
Conversation
Hey, Kieran. Attribute lines have to appear at the end of the media description, but as far as I know there is no ordering requirement for the |
I believe this positioning is required by RFC 5888 section 6: https://datatracker.ietf.org/doc/html/rfc5888#section-6 |
I must be missing something as I can't see anything in section 6 or section 3 that says the |
I don't think it's clear in any RFC or SMPTE documents but if the definition of a group contains the values between a=group...XXX...a=mid:1...XXX...a=mid:2, any new "m=" lines must therefore have a=group or a=mid preceding such lines. SMPTE RP 2110-23 does seem to try and explain this actually. |
You are right though, some people are saying the group is defined as all the lines between m= and the next m=, but some are using the a:mid lines as the boundaries for a group. |
I think this interpretation is incorrect. One media description is all the lines between one |
I agree that the RFC wants delimitation via "m=". However SMPTE RP 2110-23 says use "a:mid=" and this appears to be what many vendors are doing. |
Oh, good grief, you're right, SMPTE RP 2110-23:2019 Section 5.3 is indeed a truly horrible misrepresentation of the underlying SDP spec. (The examples are also flawed as they don't at least call out that the blank lines included are not actually permitted in SDP data and the |
No description provided.